Configuring the vault scheduled export task

This scheduled task runs the Meridian Enterprise export processor to create and transfer briefcases to remote collaborating sites. A parameter in the command line of the task specifies which transfers to process. Because checking which documents to send to each remote site is a considerable amount of work, this process should be scheduled infrequently, for example, once every 24 hours.

The task command line should have the following parameters:

• The name of the .ini file that contains the processing settings that you configured as described in Configuring the Meridian Enterprise processors.
• The destination SharePoint library's Global Collaboration Framework share name that you configured as described in Sharing the SharePoint site.
• Scheduled – Causes processing of only scheduled transfers
• True – Causes processing of all transfers, including scheduled transfers

If the .ini file is located in the same folder as the vault export processor, the path can be omitted.

Note    Installing the processors as described in Installing the Meridian Enterprise processors installs sample .cmd files for export and import with the correct .ini file names and share names that you can use to compose the command line.

Following is an example of a scheduled export task command line:

"C:\GCF\Meridian\Processors\GCFExportStarter.exe" GCFProc.INI Scheduled

"C:\GCF\Meridian\Processors\GCFExportProc.exe" <MeridianIniFile> <SharePointGCFShareName> True

Note    On Windows Server 2008, multiple instances of GCFExportProc.exe can exist for the same target share. The export processor starts and fails to find an existing instance. This can occur only when GCFExportLauncher.exe is used to export to all available shares.

To work around this issue, instead of scheduling two export tasks (one for scheduled execution and one for immediate execution), schedule two tasks for each target share name. For example, assuming three GCF sites: SiteA, SiteB, and SiteC synchronized by two tasks with command lines similar to the following:

GCFExportLauncher.exe gcf.ini scheduled
GCFExportLauncher.exe gcf.ini

Replace them with four tasks for each site with command lines similar to the following:

GCFExportProc.exe gcf.ini SiteB true
GCFExportProc.exe gcf.ini SiteC true
GCFExportProc.exe gcf.ini SiteB false
GCFExportProc.exe gcf.ini SiteC false

The first two tasks perform SiteA scheduled updates, the second two tasks perform SiteA immediate updates. Create four similar tasks on each of SiteB and SiteC.